session management method, interworking method, and network device

专利摘要:
The modalities of this application provide a method of session management, a method of interworking between different systems, and a network device. The session management method includes: when establishing a guaranteed bit rate (GBR) flow from a terminal device in a first communications system, determining, by a session management network element in the first communications system, that the GBR stream is the GBR stream needed to transfer the terminal device from the first communications system to a second communications system; and establishing, through the session management network element for the GBR flow, a session context corresponding to the second communications system. The methods and the network device are used to solve a technical problem of wasting resources existing in a transfer method in the prior art.
公开号:BR112020003199A2
申请号:R112020003199-2
申请日:2018-07-23
公开日:2020-10-06
发明作者:Yang Xin；Xiaobo Wu；Weiwei CHONG
申请人:Huawei Technologies Co., Ltd.；
IPC主号:

专利说明:

[001] [001] This application refers to the field of wireless communications technologies and, in particular, a session management method, a method of interworking between different systems and a network device. FUNDAMENTALS
[002] [002] In a 5th generation mobile communication technology network (5th Generation, 5G), to ensure interoperability between the 5G network and a 4th generation mobile communication technology network (4th Generation, 4G) or another network (such as as a 2nd generation mobile communication technology network (2nd Generation, 2G) or a 3rd generation mobile communication technology network (3rd Generation, 3G), a procedure similar to that of interworking between the network is used 4G and the 3G network or between the 4G network and the 2G network. For example, a transfer is performed using a mobility management context mapping solution (Mobility Management, MM) or session management context mapping solution (Session Management, SM).
[003] [003] However, there is a problem of wasting resources in such a solution in which transfer is performed through context mapping. SUMMARY
[004] [004] The modalities of this application provide a session management method, an interworking method and a network device, to solve a technical problem of wasting resources existing in a state of the art transfer method.
[005] [005] According to a first aspect, a session management method is provided. In the method, when establishing a guaranteed GBR bit rate stream from UE, a first session management network element needs to determine the GBR stream, to determine whether the GBR stream is a GBR stream needed to transfer the UE from a first communications system to a second communications system. If the GBR stream is determined to be the GBR stream needed to transfer the UE from the first communications system to the second communications system, the session management network element establishes a session context for the GBR stream corresponding to the second communications system.
[006] [006] In the previous technical solution, when a GBR flow is established, the session management network element needs to establish, for only the GBR flow that needs to be switched to the second communications system, a session context corresponding to the second communications system, and does not establish, for a GBR stream that does not need to be switched to the second communications system, a session context corresponding to the second communications system. Likewise, the session management network element does not need to maintain the session context that corresponds to the second communications system and that is from the GBR stream that does not need to be switched to the second communications system, in order to reduce consumption of resources.
[007] [007] In a possible implementation, the session management network element determines, based on at least one PCC load and policy control rule, an operator policy, and a DNN data network name, that the flow GBR is the GBR stream needed to transfer the terminal device from the first communications system to the second communications system.
[008] [008] In the previous technical solution, the session management network element can determine, in a plurality of ways, whether the GBR stream is the GBR stream necessary to transfer the terminal device from the first communications system to the second system communications. For example, the session management network element can perform the determination using the PCC rule, or using the operator policy, or with reference to the PCC rule, the operator policy and the DNN. Therefore, the session management network element can flexibly select a determinant method based on an actual situation.
[009] [009] In a possible implementation, the session management network element receives CCP rule information sent from a policy control network element, where the CCP rule information includes a CCP rule that is from the GBR flow and that corresponds to the second communications system. The session management network element determines, based on the PCC rule information, that the GBR stream is the GBR stream needed to transfer the terminal device from the first communications system to the second communications system.
[0010] [0010] In the previous technical solution, the session management network element can determine, using the PCC rule received from the policy management network element, whether the GBR stream is the GBR stream needed to transfer the terminal device from the first communications system to the second communications system. In this way, a computation amount of the session management network element can be reduced, and a processing speed of the session management network element can be accelerated.
[0011] [0011] In a possible implementation, the session management network element receives service information sent by the terminal device, and the session management network element determines, based on the service information, the operator policy, and the DNN data network name, that the GBR stream is the GBR stream needed to transfer the terminal device from the first communications system to the second communications system.
[0012] [0012] In the previous technical solution, the session management network element directly determines, using the service information sent by the terminal device and with reference to the operator policy and DNN, whether the GBR flow is the required GBR flow to transfer the terminal device from the first communications system to the second communications system. In this way, the time taken for interaction between the session management network element and another network element can be reduced, thereby speeding up the processing speed of the entire communications system.
[0013] [0013] In a possible implementation, the PCC rule includes a GBR parameter, an MBR multi-band indicator parameter and an IP filter.
[0014] [0014] In the previous technical solution, the CCP rule includes different specific content, and the aforementioned represents merely several examples. This is not limited in this mode of this application.
[0015] [0015] According to a second aspect, a session management method is provided. In the method, a policy control network element receives service information from a terminal device or an application network element, and then generates policy control and PCC load rule information based on at least one of a operator policy and DNN data network name, service information, and an interworking capability of the terminal device from a first standard communications network to a second standard communications network. The PCC rule information includes at least one PCC rule that is from the GBR stream and that corresponds to a first communications system. The first communications system uses the first standard communications network, and the second communications system uses the second standard communications network. Finally, the policy management network element sends the generated CCP rule to a session management network element.
[0016] [0016] In the preceding technical solution, the policy management network element can determine, in a plurality of ways, whether the GBR stream is a GBR stream necessary to transfer the terminal device from the first communications system to the second system communications. For example, the policy management network element can perform determination using operator policy, service information,
[0017] [0017] In a possible implementation, the PCC rule includes a GBR parameter, an MBR multi-band indicator parameter and an IP filter.
[0018] [0018] In the previous technical solution, the CCP rule includes different specific content, and the aforementioned represents merely several examples. This is not limited in this mode of this application.
[0019] [0019] In accordance with a third aspect, an interworking method is provided. In the method, a session management network element in a first communications system receives first session context request information sent from an access management network element in the first communications system. The session context request information is used to obtain a session context that is from a terminal device in the first communications system and that corresponds to a second communications system. The session management network element then determines whether there is a dedicated quality of service flow in a session corresponding to the session context request, and then sends the session context in the session to the access management network element. which there is a dedicated service quality flow.
[0020] [0020] In the previous technical solution, if there is no dedicated quality of service flow in the session, the session management network element does not need to send the session context to the access management network element. Therefore, a PDN connection to the session context in which there is no dedicated quality of service flow does not need to be established in the second communications system, thereby reducing signaling and channel resources.
[0021] [0021] In a possible implementation, if the session management network element determines that there is no dedicated quality of service flow in the session corresponding to the session context request, the session management network element releases the session on which there is no dedicated service quality flow.
[0022] [0022] In the previous technical solution, if there is no dedicated flow of quality of service in the session context, the session management network element directly releases the session, in order to further reduce channel resources.
[0023] [0023] In a possible implementation, if the session management network element determines that there is no SDF service data flow in the standard quality of service flow in the session corresponding to the session context request, the management network element session releases the session in which there is no SDF in the standard quality of service flow.
[0024] [0024] In the previous technical solution, if there is no SDF in the standard quality of service flow in the session, that is, the session has no service, the session management network element directly releases the session, in order to further reduce channel resources.
[0025] [0025] In a possible implementation, if the session management network element determines that there is an SDF service data flow in the standard quality of service flow in the session corresponding to the session context request, the management network element The session context sends, to the access management network element in the first communications system, the session context corresponding to the session in which the SDF exists.
[0026] [0026] In the previous technical solution, if the SDF exists in the standard quality of service flow in the session, that is, the session still processes a service, the session management network element sends it to the access management network element in the first communications system, the session context corresponding to the session, in order to avoid omission of service data.
[0027] [0027] According to a fourth aspect, an interworking method is provided. In the method, an access management network element sends session context request information to a session management network element in a first communications system, where session context request information is used to obtain context session that is from a terminal device in the first communications system and that corresponds to a second communications system. Then, the access management network element receives the session context sent by the session management network element, and there is a dedicated quality of service flow in a session corresponding to the session context.
[0028] [0028] In the previous technical solution, after the access management network element sends the session context request to the session management network element in the first communications system, the access management network element can receive only one context corresponding to the session in which the dedicated quality of service flow exists. In this way, a PDN connection to the session context in which there is no dedicated quality of service flow does not need to be established in the second communications system, in order to reduce signal and channel resources.
[0029] [0029] According to a fifth aspect, one embodiment of this request provides a network device, and the network device has functions to implement behaviors of the session management network element in the method in the first aspect. The functions can be implemented using hardware, or they can be implemented by running the corresponding hardware software. The hardware or software includes one or more modules corresponding to the functions.
[0030] [0030] In a possible design, a network device structure includes a processor and a transmitter, and the processor is configured to support the network device in performing corresponding functions in the method in the first aspect. The transmitter is configured to support communication between the network device and another device, and to send information or an instruction in the method in the first aspect to the other device. The network device may also include a memory. The memory is configured to be coupled to the processor. The memory stores a required instruction and program data.
[0031] [0031] According to a sixth aspect, one embodiment of this request provides a network device, and the network device has functions to implement behaviors of the policy control network element in the method in the second aspect. The functions can be implemented using hardware. A network apparatus structure includes a processor, a transmitter and a receiver. The functions can alternatively be implemented by running corresponding hardware software. The hardware or software includes one or more modules corresponding to the functions. The module can be software and / or hardware.
[0032] [0032] In a possible design, a network device structure includes a processor and a transmitter, and the processor is configured to support the network device in performing corresponding functions in the method in the second aspect. The transmitter is configured to support communication between the network device and another device, and to send information or an instruction in the method in the second aspect to the other device. The network device may also include a memory. The memory is configured to be coupled to the processor. The memory stores a required instruction and program data.
[0033] [0033] According to a seventh aspect, one embodiment of this request provides a network device, and the network device has functions to implement behaviors of the session management network element in the method in the third aspect. The functions can be implemented using hardware, or they can be implemented by running corresponding hardware software. The hardware or software includes one or more modules corresponding to the functions.
[0034] [0034] In a possible design, a network device structure includes a processor and a transmitter, and the processor is configured to support the network device in performing corresponding functions in the method in the third aspect. The transmitter is configured to support communication between the network device and another device, and to send information or an instruction in the method in the third aspect to the other device. The network device may also include a memory. The memory is configured to be coupled to the processor. The memory stores a required instruction and program data.
[0035] [0035] According to an eighth aspect, one embodiment of this request provides a network device, and the network device has functions to implement behaviors of the access management network element in the method in the fourth aspect. The functions can be implemented using hardware. A network apparatus structure includes a receiver, a transmitter and a processor. The functions can alternatively be implemented by running corresponding hardware software. The hardware or software includes one or more modules corresponding to the functions. The module can be software and / or hardware.
[0036] [0036] In a possible design, a network device structure includes a processor and a transmitter, and the processor is configured to support the network device in performing corresponding functions in the method in the fourth aspect. The transmitter is configured to support communication between the network device and another device, and to send information or an instruction in the method in the fourth aspect to the other device. The network device may also include a memory. The memory is configured to be coupled to the processor. The memory stores a required instruction and program data.
[0037] [0037] According to a ninth aspect, one embodiment of this request provides a communications system, and the system includes the network apparatus described in the first and second aspects, and / or the network apparatus described in the third aspect and in fourth aspect.
[0038] [0038] According to a tenth aspect, one embodiment of this application provides a computer storage medium, configured to store a computer software instruction used to perform functions of the first aspect, any project of the first aspect, of the second aspect, of the third aspect and fourth aspect, and include a program designed to execute the methods in the first aspect, any project of the first aspect, the second aspect, the third aspect and the fourth aspect.
[0039] [0039] According to an eleventh aspect, one embodiment of this application provides a computer program product, and the computer program product includes an instruction. When the instruction is executed on a computer, the computer executes the methods in the first aspect, any project of the first aspect, the second aspect, the third aspect and the fourth aspect.
[0040] [0040] According to a twelfth aspect, one embodiment of this application also provides a chip system, and the chip system includes a processor, configured to support a network device in implementing the method in any of the preceding aspects, for example , generate or process data and / or information in the previous method. In a possible project, the chip system also includes a memory, and the memory is configured to store an instruction and program data that are needed by the network device. The chip system can include a chip, or it can include a chip and another discrete device. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] [0041] FIG. 1 is an architectural diagram of the interworking between a 5G network and a 4G network; FIG. 2 is a flowchart of a session management method according to an embodiment of this request; FIGS. 3A and 3B are a flowchart of an instance of a session management method according to an embodiment of this request; FIGS. 4A and 4B are a flowchart of another instance of a session management method according to an embodiment of this request; FIGS. 5A and 5B are a flow chart of an interworking method according to an embodiment of this application; and FIGS. 6 to 13 are structural diagrams of a network device according to an embodiment of this application. DESCRIPTION OF MODALITIES
[0042] [0042] The technical solutions in the modalities of this application are clearly described below with reference to the attached drawings in the modalities of this application.
[0043] [0043] Modalities of this application provide a method of session management in a method of interworking between different systems, and the methods are applied to an architecture of interworking with different systems. The interworking architecture specifically includes two different communications systems, such as a 5G network and a 4G network, and it can certainly include other communications systems such as a new radio system (New Radio, NR), a Wireless Loyalty system (Wi-Fi), a Worldwide Interoperability System for Microwave Access (Worldwide Interoperability for Microwave Access, WiMAX), a global system for mobile communications (Global System of Mobile communication, GSM), a Division Multiple Access system Code (Multiple Division Access, CDMA), a Wideband Code Division Multiple Access, WCDMA, a general packet radio service system (General Packet Radio Service, GPRS) , a Long Term Evolution (LTE) system, an Advanced Long Term Evolution system (LTE-A), a Universal Mobile Telecommunications System ( Universal Mobile Telecommunication System, UMTS), and a cellular system related to the 3rd Generation Partnership Project (The 3rd Generation Partnership Project, 3GPP). The inter-RAT system can be any two of the preceding communications systems.
[0044] [0044] In addition, the interworking architecture is still applicable to a future-oriented communication technology. The systems described in the modalities of this application are intended to describe more clearly the technical solutions in the modalities of this application, and are not a limitation to the technical solutions provided in the modalities of this application. A person skilled in the art may know that with the evolution of network architectures, the technical solutions provided in the modalities of this application are also applicable to a similar technical problem.
[0045] [0045] With reference to FIG. 1, FIG. 1 is an architecture of a non-mobile interworking scenario between a 5G network and an evolved packet core (EPC) / an evolved universal terrestrial radio access network (Evolved Universal Terrestrial Radio Access Network, E-UTRAN ), and is a specific scenario for applying the modalities of this request.
[0046] [0046] Functions of network elements in the interworking architecture shown in FIG. 1 are described below.
[0047] [0047] The radio access network (RAN) 5G is a network that includes a plurality of RAN 5G nodes, and implements a physical radio layer function, resource scheduling and radio resource management, radio access control, and a mobility management function. The 5G RAN is connected to a user plane function (UPF) network element via an N3 user plane interface to transfer data from the UE. The RAN establishes a control plan signaling connection to an Access and Mobility Management Function (AMF) network element of the basic network through an N2 control plan interface to implement functions such as radio access carrier control.
[0048] [0048] An AMF network element is primarily responsible for functions such as UE authentication, UE mobility management, network slice selection, and selection of a session management function network element. As an anchor to connect N1 signaling and N2 signaling, the AMF network element also directs session management messages (Session Management, SM) from N1 and N2 to the SMF network element, and maintains and manages status information. HUH.
[0049] [0049] An SMF network element is connected to the AMF network element via an N11 interface, and is primarily responsible for all control plane functions in the UE session management, including selection of a function network element User Plan Function (UPF), Internet Protocol (IP) address allocation, management of a session's Quality of Service (QoS) attributes, and obtaining a policy control and loading (Policy Control and Charging, PCC) from a policy control function network element (Policy Control Function, PCF).
[0050] [0050] A PCF network element is connected to the SMF network element through an N7 interface, and connected to the AMF network element through an N15 interface. The PCF network element is configured to generate and store a PCC rule related to session management and provides the PCC rule to the SMF network element, and is further configured to generate policy information regarding mobility management and provide the policy information to the AMF network element.
[0051] [0051] A user data management network element (User Data Management, UDM) is connected to the AMF network element via an N8 interface, and connected to the SMF network element via an N10 interface. The user data management network element is configured to store subscription information for a user, and provide parameter information regarding subscription to the corresponding network elements separately via the N8 interface and the N10 interface.
[0052] [0052] A UPF network element is connected to the SMF network element via an N4 interface. The UPF network element serves as a session connection anchor for a protocol data unit (Protocol Data Unit, PDU), and is responsible for filtering data packets, transmitting or forwarding data, rate control, and generation of loading information that is for the UE.
[0053] [0053] A service portal (Serving Gateway, SGW) is connected to the UPF network element via an S5-U interface, and connected to the SMF network element via an S5-U interface. The service portal is configured to direct and forward a data packet according to the control of a mobility management network element (Mobility Management Entity, MME).
[0054] [0054] An MME network element is connected to the UDM network element through an S6a interface, connected to SGW through an S11 interface and connected to E-UTRAN through an S1-MME interface. The MME network element is primarily responsible for functions such as mobility management, support management, user authentication, and selecting an SGW and PGW. When single registration is performed on a 5G network and a 4G network, the transfer performed between the MME network element and the AMF network element is supported by the use of an N26 interface. Of course, transfer between the MME network element and the AMF network element can also be supported using another interface. This is not limited in this document.
[0055] [0055] The E-UTRAN is connected to the SGW through an S1-U interface, and connected to the MME through the S1- MME interface. The S1-MME interface is a control plane protocol reference point between E-UTRAN and MME, and the S1-U interface is a user plane tunnel reference point for each carrier between E-UTRAN and SGW.
[0056] [0056] It should be understood that all network elements shown in FIG. 1 can be independent of each other, or two or more network elements can be integrated together. This is not specifically limited in this embodiment of this application.
[0057] [0057] A terminal device mentioned in this specification can be a wireless terminal device or it can be a wired terminal device. The wireless terminal device can be a device that provides voice and / or other service data connectivity to a user, a portable device with a wireless connection function, or another processing device connected to a wireless modem. The wireless terminal device can communicate with one or more basic networks using a radio access network (Radio Access Network, RAN). The wireless UE can be a mobile terminal such as a mobile phone (or referred to as a "cell phone") or a computer with a mobile terminal. For example, the mobile terminal device can be a portable, handheld, handheld, built-in computer, or vehicle mobile device that exchanges a voice and / or data with the radio access network. For example, the wireless terminal device may be a device such as a Personal Communications Service (PCS) telephone, a wireless telephone device, a Session Initiation Protocol, SIP telephone ), a wireless local loop station (Wireless Local Loop, WLL), or a personal digital assistant (Personal Digital Assistant, PDA). The wireless UE can also be referred to as a system, a subscriber unit (Subscriber Unit), a subscriber station (Subscriber Station), a mobile station (Mobile Station), a remote station (Remote Station), a remote terminal ( Remote Terminal), an access terminal (Access Terminal), a user terminal (User Terminal), a user agent (User Agent), user equipment (User Device), or user equipment (User Equipment).
[0058] [0058] In the following description, the fact that the terminal device is UE is used as an example for description. In addition, the term “and / or” in this specification describes only one association relationship to describe associated objects and represents that there can be three relationships. For example, A and / or B can represent the following three cases: only A exists, both A and B exist, and only B exists. In addition, the “/” character in this specification generally indicates an “or” relationship between associated objects.
[0059] [0059] The 4G network and the current 5G network are used as an example for some abbreviations in English in this specification to describe the modalities of this request, and the abbreviations in English may change with the evolution of networks. For specific developments, refer to the descriptions in a corresponding standard.
[0060] [0060] The architecture shown in FIG. 1 is used below as an example to describe a process, in the prior art, or transferring UE from a 5G network to a 4G network.
[0061] [0061] To ensure continuity of service from the UE after a system transfer, the execution of the system transfer to the UE is to substantially transfer, for the 4G network, parameters corresponding to a session of the data packet unit (Packet Data Unit, PDU ) of the UE on the 5G network, such as an evolved packet core carrier number (EPS bearer ID), a quality of service parameter (Quality of Service, QoS), and a traffic flow template (traffic flow template, TFT), so that a corresponding EPS carrier can be quickly established on the 4G network based on the parameters, and a service is further provided to the UE using the 4G network.
[0062] [0062] The parameters corresponding to the PDU session are briefly described below.
[0063] [0063] A PDU session includes the following parameters.
[0064] [0064] (a) The PDU session has only a standard quality of service flow (default QoS flow). The standard QoS flow is created during the establishment of the PDU session. Main QoS parameters include a 5G quality of service identifier (5G QoS Identifier, 5QI), a quality of service flow ID (QoS Flow ID, QFI), and an allocation and retention priority (Allocation And Retention Priority, ARP ). At least one service data flow (Service Data Flow, SDF) can be aggregated into a standard QoS flow, and SDFs have a common 5QI and ARP.
[0065] [0065] (b) The PDU session may include one or more non-guaranteed Bit Rate QoS flows, non-GBR QoS flow. The non-GBR QoS flow is created in a PDU session modification procedure initiated on one side of the UE or one side of the network. Main QoS parameters include a 5QI, a QFI, a maximum bit rate (Maximum Bit Rate, MBR), an ARP and an IP link filter (UL + DL IP filter). A non-GBR QoS stream has at least one SDF, and another or more SDFs can also be aggregated into the non-GBR QoS stream. SDFs have a common 5QI and ARP.
[0066] [0066] (c) The PDU session may include one or more flows of guaranteed bit rate quality of service (Guaranteed Bit Rate QoS flow, GBR QoS flow). The GBR QoS flow is created in a PDU session modification procedure initiated on one side of the UE or one side of the network. Main QoS parameters include a 5QI, a QFI, a GBR, an MBR, an ARP, an UL + DL IP filter, and a TFT. A GBR QoS stream has at least one SDF, and another or more SDFs can also be aggregated into the non-GBR QoS stream.
[0067] [0067] In the state of the art, before the UE is transferred from the 5G network to the 4G network, one side of the 5G network prepares the standard QoS flow and the GBR QoS flow. That is, when the UE is transferred to the 4G network, corresponding session management contexts (Session Management, SM) of an evolved packet core standard carrier (Default EPS Bearer) and an evolved packet core carrier are prepared. guaranteed bit rate (GBR EPS Bearer). The SM context includes an evolved packet core carrier number (EPS Bearer ID) and a QoS parameter that includes a TFT.
[0068] [0068] In a process of transferring from the 5G network to the 4G network, an access and mobility management function (AMF) network element selects a portion of the GBR QoS flow prepared based on a data network name (Data Network Name, DNN), a quality of service profile (QoS profile), or an operator policy, and switch the part of the QoS flow from GBR to the 4G network, to complete the transfer .
[0069] [0069] Before the UE is transferred from the 5G network to the 4G network, an SM context that corresponds to each GBR QoS stream and that is on the 4G network needs to be maintained on the 5G network. For example, when a QoS parameter is updated, or in a process of transferring the UE between a plurality of 5G networks, or when an SMF is relocated, the 5G network modifies the corresponding SM context that is from the GBR QoS stream and that is on the 4G network.
[0070] [0070] However, a maximum number of EPS carrier IDs from a UE is 8 on the 4G network, and a number of standard QoS streams and GBR QoS streams from a UE on the network.
[0071] [0071] In a first aspect, before the transfer is performed, the SM contexts corresponding to the unselected GBR QoS flows are also maintained in the 5G network, but the maintained SM contexts are finally not used in the 4G network. This is equivalent to wasting resources used to maintain SM contexts on the 5G network. Therefore, there is a technical problem of wasting resources in the transfer method in the prior art.
[0072] [0072] In view of this, the modalities of this request provide a method of session management. In the method, when establishing a guaranteed GBR bit rate stream from UE, a session management network element first needs to assess the GBR stream, to determine whether the GBR stream is a GBR stream required for transferring the UE from a first communications system to a second communications system. If the GBR stream is determined to be the GBR stream required to transfer the UE from the first communications system to the second communications system, the session management network element establishes a session context for the GBR stream corresponding to the second communications system. Thus, when a GBR stream is established, the session management network element needs to establish, for only one GBR stream that needs to be switched to the second communications system, a session context corresponding to the second communications system, and does not establish, for the GBR stream that does not need to be transferred to the second communications system, a session context corresponding to the second communications system. Likewise, the session management network element does not need to maintain the session context that corresponds to the second communications system and that is from the GBR stream that does not need to be transferred to the second communications system, in order to reduce consumption of resources.
[0073] [0073] The method provided in the modalities of this application is described below with reference to the attached drawings. With reference to FIG. 2, FIG. 2 is a flowchart of a session management method according to an embodiment of this request. The method can be applied to the interworking architecture of different systems shown in FIG. 1.
[0074] [0074] It should be noted that network elements in this embodiment of this application can be corresponding network elements in FIG. 1. Of course, if the method is applied to a different interworking architecture, a session management network element can also be another network element. This is not limited in this document. For example, when the method is applied to the architecture shown in FIG. 1, the session management network element may be the SMF network element in FIG. 1, a policy control network element may be the PCF network element in FIG. 1, and an access management network element may be the AMF network element in FIG. 1, and so on. In the following description, an example is used in which the network elements in the method are the corresponding network elements in FIG. 1. The method can include the following steps.
[0075] [0075] Step 201: An SMF network element determines that the GBR flow needs to be established.
[0076] [0076] In this embodiment of this request, the GBR stream may be a GBR QoS stream, or it may be another GBR stream. In this embodiment of this request, an example in which the GBR stream is a GBR QoS stream is used for description.
[0077] [0077] It should be noted that a GBR QoS flow is established in a PDU session modification procedure. Therefore, the fact that the SMF network element determines whether a GBR QoS flow needs to be established determines whether the PDU Session Modification procedure needs to be initiated.
[0078] [0078] The SMF network element can be triggered to initiate the PDU session modification procedure in any of the following ways: in a first possible implementation, the UE initiates the PDU session modification procedure. The UE sends a stratum message (Non-Access Stratum, NAS) to an AMF network element. The NAS message includes a PDU session ID and an N1 SM message that carries a PDU session modification request. The AMF network element then triggers an Nsmf_PDUSession_UpdateSMContext service operation based on the NAS message, to send the PDU session ID and the N1 SM message that carries the session change request to the SMF network element. of PDU. After receiving the message sent by the AMF network element, the SMF network element starts the PDU session modification procedure and determines that the GBR QoS flow needs to be established.
[0079] [0079] It should be noted that if the UE is in an inactive state of CN, that is, no air interface resource is established between the UE and a RAN, the NAS message needs to be sent to the AMF network element using a 5G network using a service request procedure. In addition, in addition to including the PDU session ID and the N1 SM message that carries the PDU session change request, the NAS message carries UE location information, for example, a RAN ID and a Cell ID (Cell). Then the AMF network element sends the NAS message to the SMF network element.
[0080] [0080] In a second possible implementation, a PCF network element initiates the PDU session modification procedure based on operator policy information and a request that comes from an application function network element (Application Function, AF). The PCF network element sends a PCC rule of a GBR QoS stream to the SMF network element using an Npcf SMPolicyControl_UpdateNotify service. After receiving the PCC rule, the SMF network element starts the PDU session modification procedure, and determines that the GBR QoS flow needs to be established. In this modality of this request, the PCC rule includes a GBR parameter, a multi-frequency band indicator parameter (Multi Band Radio, MBR) and an IP filter, or the PCC rule may be a delay requirement.
[0081] [0081] In a third possible implementation, when updating UE subscription data, a UDM network element sends a permanent subscriber identity (Subscriber Permanent Identity) and subscriber data (Subscription Data) to the SMF network element using a Nudm_SubscriberData_UpdateNotification service. After receiving the subscriber information, the SMF network element triggers the PDU session modification procedure, determines that a GBR QoS flow needs to be established, updates the UE subscription data, and responds to the UDM network element by adding the permanent subscriber identity of the UE to an acknowledgment message.
[0082] [0082] In a fourth possible implementation, the SMF network element can determine, based on a locally configured policy, to modify a PDU session. Therefore, the SMF network element initiates the PDU session modification procedure, and determines that the flow of
[0083] [0083] In a fifth possible implementation, if Notification Control is configured for a GBR QoS flow in a 5G RAN, and the 5G RAN determines that a GBo QoS flow QoS parameter cannot be satisfied in RAN 5G, RAN 5G sends an N2 message to an AMF network element. The N2 message includes a PDU session ID and N2 SM information. The N2 SM information includes a QFI, UE location information, and a notification message, in order to notify, using the notification message, the AMF network element that the QoS parameter of the GBR QoS stream does not can be satisfied in the RAN 5G. In this case, the AMF network element triggers an Nsmf_PDUSession_UpdateSMContext service operation, to send the N2 SM message to the SMF network element. After receiving the message sent by the AMF network element, the SMF network element starts the PDU session modification procedure, and determines that a GBR QoS flow needs to be established.
[0084] [0084] Step 202: The SMF network element determines that the GBR stream is a GBR stream necessary for transferring the UE from a 5G network to a 4G network.
[0085] [0085] After the SMF network element initiates the PDU session modification procedure, the SMF network element needs to determine the GBR QoS flow corresponding to the PDU session modification procedure, to determine whether the QoS flow from GBR is a GBR QoS stream needed to transfer the UE from the 5G network to the 4G network.
[0086] [0086] Specifically, the SMF network element can determine, based on at least one of a CCP rule, an operator policy, and a DNN, that the GBR QoS flow is the GBR QoS flow required for transfer from the EU from 5G to 4G.
[0087] [0087] In a possible implementation, when determining, based on a PCC rule, whether the GBR QoS flow is the GBR QoS flow required to transfer the UE from 5G to 4G, the SMF network element can execute the determination of whether a PCC rule corresponding to the GBR QoS flow includes a 4G PCC rule. If the PCC rule corresponding to the GBR QoS flow includes the 4G PCC rule, the GBR QoS flow is the GBR QoS flow required to transfer the UE from 5G to 4G. If the PCC rule corresponding to the GBR QoS flow does not include the 4G PCC rule, the GBR QoS flow is not the GBR QoS flow required to transfer the UE from 5G to 4G.
[0088] [0088] In a possible implementation, when the SMF network element determines that the PCC rule corresponding to the GBR QoS flow includes a delay requirement, if the SMF network element determines that the delay requirement in the PCC rule is relatively high, the SMF network element determines that the GBR QoS flow is not the GBR QoS flow required to transfer the UE from 5G to 4G. If the SMF network element determines that the delay requirement in the PCC rule is relatively low, the SMF network element determines that the GBR QoS flow is the GBR QoS flow required to transfer the UE from 5G to 4G.
[0089] [0089] In a possible implementation, when determining, based on an operator policy, whether the GBR QoS flow is the GBR QoS flow required to transfer the UE from 5G to 4G, the SMF network element can determine whether a service type corresponding to the GBR QoS flow is a service type supported by a network operator policy. For example, a 4G network operator policy supports a type of video data download service, and does not support a type of real-time communication service such as automatic driving, an AR / VR application, or a touch network. . If the type of service corresponding to the GBR QoS flow is automatic driving, the SMF network element determines that the GBR QoS flow is not the GBR QoS flow required to transfer the UE from 5G to 4G. If the type of service corresponding to the GBR QoS stream is video data download, the SMF network element determines that the GBR QoS stream is the GBR QoS stream required to transfer the UE from 5G to 4G.
[0090] [0090] In a possible implementation, when the SMF network element determines, based on a DNN, whether the GBR QoS flow is the GBR QoS flow required to transfer the UE from 5G to 4G, the network element SMF can pre-store a match between each DNN and whether a GBR QoS stream corresponding to the DNN needs to be transferred to the 4G network. For example, a Vehicle Internet needs to be transferred to the 4G network, but machine-to-machine (Machine-to-Machine, M2M) or an Internet of Things (Internet of Things, IoT) does not need to be transferred to the 4G network . Thus, after determining a DNN corresponding to the GBR QoS flow, the SMF network element determines, based on the correspondence between the DNN and whether the GBR QoS flow corresponding to the DNN needs to be transferred to the 4G network, if the GBR QoS flow is the GBR QoS flow required to transfer the UE from 5G to 4G. For example, the pre-stored correspondence by the SMF network element is that the Vehicle Internet needs to be transferred to the 4G network, but machine-to-machine (Machine-to-Machine, M2M) or an Internet of Things (Internet of Things, IoT) does not need to be transferred to the 4G network. If the DNN corresponding to the GBR QoS flow is the Vehicle Internet, the SMF network element determines that the GBR QoS flow is the GBR QoS flow required to transfer the UE from 5G to 4G. If the DNN corresponding to the GBR QoS flow is the Internet of Things, the SMF network element determines that the GBR QoS flow is not the GBR QoS flow required to transfer the UE from 5G to 4G
[0091] [0091] Certainly, it can be determined, by combining any two or three of the preceding plurality of modes, whether the GBR QoS flow is the GBR QoS flow required for transferring the UE from 5G to 4G. This is not limited in this mode of this application.
[0092] [0092] It should be noted that each of the preceding plurality of modes of determination can also correspond to a plurality of specific implementations, and the plurality of specific implementations is not listed one by one in this modality of this application.
[0093] [0093] An example in which the SMF network element performs determination based on a PCC rule is used below for specific description.
[0094] [0094] In a specific implementation process, the SMF network element can perform determination in the following way.
[0095] [0095] The SMF network element performs determination based on a PCC rule obtained from the PCF network element.
[0096] [0096] In this modality of this request, since the ways of activating the SMF network element to initiate the PDU session modification procedure are different, methods of obtaining the PCC rule from the PCF network element by the network element SMF are also different.
[0097] [0097] Obtaining method 1: if the SMF network element is triggered to initiate the PDU session modification procedure using the first or fifth possible implementations, the N1 SM message or the N2 SM message received by the SMF network element carries a QoS parameter of a GBR QoS stream that needs to be established for the UE. When the SMF network element determines that a dynamic PCC rule is implemented in the PCF network element, the SMF network element sends the obtained QoS parameter to the network element
[0098] [0098] If the PCF network element determines that the GBR QoS flow needs to be transferred to the 4G network, the PCF network element allocates a corresponding 5G PCC rule and a corresponding 4G PCC rule to the GBR QoS flow , including a 5G QoS parameter and a 4G QoS parameter. The QoS parameter includes information such as a QCI, a GBR, an MBR, an ARP, precedence, and an uplink / downlink TFT. Alternatively, if the PCF network element determines that the GBR QoS flow does not need to be transferred to the 4G network, the PCF network element allocates only one corresponding 5G PCC rule to the GBR QoS flow, and does not allocate a corresponding one. 4G CCP rule to GBR QoS flow. The PCF network element then sends a generated PCC rule to the SMF network element, so that the SMF network element obtains, from the PCF network element, the PCC rule corresponding to the GBR QoS flow. The PCC rule includes the PCC 5G rule, or the PCC rule includes the PCC 5G rule and the PCC 4G rule.
[0099] [0099] Obtaining method 2: if the SMF network element is triggered to initiate the PDU session modification procedure using the second possible implementation, the PCF network element receives service information from the UE sent by the AF network element. Service information includes IP filtering information, media information (bandwidth, instability, a delay, and the like), and the like. The PCF network element then generates a 5G PCC rule based on the service information. The 5G PCC rule includes a 5G QoS parameter, such as a QCI, GBR, MBR, ARP, and uplink / downlink packet filtering information. If the PCF determines that the generated 5G QoS parameter includes GBR information used to establish a GBR QoS flow, the PCF network element determines, based on at least one piece of information in a DNN and operator policy information , the QoS parameter, indication information indicating interworking between a first standard communications network and a second standard communications network, and similar, if the QoS flow of GBR to be established needs to be transferred to the 4G network. The indication information that indicates interworking between the first standard communications network and the second standard communications network includes recordability information that indicates that the UE, the SMF network element, and the AMF network element support single registration, and / or the UE supports a stratum mode without NAS access applicable to the first standard communications network and a NAS mode applicable to the second standard communications network. If the PCF network element determines that the GBR QoS flow needs to be transferred to the 4G network, the PCF network element allocates a corresponding 4G PCC rule to the GBR QoS flow, including a GBR QoS parameter. The 4G QoS parameter includes information such as a QCI, a GBR, an MBR, an ARP, precedence, and an uplink / downlink TFT. Alternatively, if the PCF network element determines that the GBR QoS flow does not need to be transferred to the 4G network, the PCF network element does not allocate a corresponding 4G PCC rule to the GBR QoS flow, and does not allocate a corresponding 4G CCP rule to GBR QoS flow. The PCF network element then sends a generated PCC rule to the SMF network element using the Npcf SMPolicyControl_UpdateNotify service, so that the SMF network element obtains, from the PCF network element, the PCC rule corresponding to the GBR QoS. The PCC rule includes the PCC 5G rule, or the PCC rule includes the PCC 5G rule and the PCC 4G rule.
[00100] [00100] After obtaining, from the PCF network element, the PCC rule corresponding to the GBR QoS flow, the SMF network element determines whether the PCC rule includes the 4G PCC rule. If the PCC rule includes the 4G PCC rule, the SMF network element determines that the GBR QoS flow is the GBR QoS flow required to transfer the UE from the 5G network to the 4G network.
[00101] [00101] An example in which the SMF network element performs determination based on an operator or DNN policy is used below for specific description.
[00102] [00102] If the SMF network element is triggered to initiate the PDU session modification procedure using the first or fifth possible implementation, the N1 SM message or the N2 SM message received by the SMF network element carries UE service information. Service information includes IP filtering information, media information (bandwidth, instability, a delay, and the like), and the like. After the SMF network element determines that a static PCC rule is deployed locally, the SMF network element generates a 5G PCC rule based on the service information. The 5G PCC rule includes a 5G QoS parameter, such as a QCI, a GBR, an MBR, an ARP, and an uplink / downlink TFT. If the SMF network element verifies that the generated 5G QoS parameter includes GBR information used to establish a GBR QoS flow, the SMF network element determines, based on at least one piece of information in a DNN and information of operator policy, the QoS parameter, indication information indicating interworking between a first standard communications network and a second standard communications network, and similar, if the GBo QoS flow to be established needs to be transferred to the 4G network. The indication information that indicates interworking between the first standard communications network and the second standard communications network includes recordability information that indicates that the UE, the SMF network element, and the AMF network element support single registration, and / or the UE supports a stratum mode without NAS access applicable to the first standard communications network and a NAS mode applicable to the second standard communications network.
[00103] [00103] After the SMF network element determines the GBR QoS flow to be established, the SMF can also map a PCC rule to the GBR QoS flow. For example, when the SMF network element determines that the GBR QoS flow needs to be transferred to the 4G network, the SMF network element maps a corresponding 4G rule to the GBR QoS flow, which includes a 4G QoS parameter . The QoS parameter includes information such as a QCI, a GBR, an MBR, an ARP, precedence, and an uplink / downlink TFT. Alternatively, if the SMF network element determines that the GBR QoS flow does not need to be transferred to the 4G network, the SMF network element does not map a corresponding 4G PCC rule to the GBR QoS flow.
[00104] [00104] It should be noted that when the SMF network element is triggered to initiate the PDU session modification procedure using the third and fourth implementation, the SMF network element can use any of the foregoing plurality of modes to determine whether the GBR QoS flow is the GBR QoS flow required to transfer the UE from the 5G network to the 4G network. Details are not described again in this document.
[00105] [00105] After the SMF network element completes the previous steps, the SMF network element allocates a corresponding 4G QoS parameter to the GBR QoS flow that needs to be transferred to the 4G network.
[00106] [00106] Step 203: The SMF network element establishes, for the GBR QoS flow, an EPS carrier ID corresponding to the 4G network.
[00107] [00107] After the SMF network element allocates the corresponding 4G QoS parameter to the GBR QoS flow that needs to be transferred to the 4G network, the SMF network element still needs to establish, for the GBR QoS flow, the ID EPS carrier corresponding to the 4G network.
[00108] [00108] In this modality of this application, two modes of establishment are mainly included.
[00109] [00109] Establishment mode 1: if the EPS carrier ID is allocated to the AMF network element, the SMF network element needs to send the AMF network element related information used to establish the EPS carrier ID that is corresponding to the QoS flow of GBR and that is in the 4G network. Since objects that trigger the SMF network element to initiate the PDU session modification procedure are different, service operations used by the SMF network element to send the related information to the AMF network element are also different. There are specifically the following two modes: (a) for a case in which the UE triggers the SMF network element to initiate the PDU session modification procedure, the SMF network element triggers the Nsmf_PDUSession_UpdateSMContext service operation with the network element AMF. An Nsmf_PDUSession_UpdateSMContext message sent by the SMF network element to the AMF network element includes at least the N2 SM message and the N1 SM message. The N2 SM message includes the PDU session ID, a quality of service profile (QoS Profile), and a Session-Aggregated Maximum Bit Rate, Session-AMBR parameter. The N1 SM message includes a session modification command. The session modification command includes a PDU session ID, a quality of service rule (QoS rule), and the AMBR session parameter. The QoS rule includes partial content of the CCP rule. For example, the QoS rule may include information such as an uplink packet filter, in the PCC rule, which is related to uplink data; (b) for a case other than the case in which the UE triggers the SMF network element to initiate the PDU session modification procedure, the SMF network element triggers the Namf_Communication_N1N2MessageTransfer service operation of the AMF network element. A Namf_Communication_N1N2MessageTransfer message sent by the SMF network element to the AMF network element includes at least the N2 SM message and the N1 SM message. The content included in the N2 SM message and the N1 SM message is the same as that in (a). Details are not described again in this document; After the AMF network element receives the preceding information sent by the SMF network element, the AMF network element allocates the EPS carrier ID in the 4G network to the QoS flow of GBR based on the preceding information.
[00110] [00110] Mode of establishment 2: if the EPS carrier ID is allocated by the UE, the SMF network element needs to send the UE related information used to establish the EPS carrier ID that corresponds to the QoS flow of GBR and that is on the 4G network. Specifically, the SMF network element first sends the related information to the AMF network element, and then the AMF network element forwards the related information to the UE. After receiving the related information, the UE allocates the EPS carrier ID to the GBR QoS stream.
[00111] [00111] Likewise, since objects that trigger the SMF network element to initiate the PDU session modification procedure are different, service operations used by the SMF network element to send the related information to the AMF network element they are also different. For details, refer to (a) or (b) in establishment mode 1. Details are not described again in this document.
[00112] [00112] After the AMF network element receives the information sent by the SMF network element, the AMF network element sends, to the RAN, information carried in the N2 SM message, and sends the N1 SM message to the UE. After receiving the N1 SM message, the UE allocates the EPS carrier ID to the GBR QoS stream based on a 4G QoS parameter in the N1 SM message.
[00113] [00113] After allocating the EPS carrier ID to the GBR QoS stream, the AMF network element or the UE can send acknowledgment information to the SMF network element, to notify the SMF network element that the allocation of the EPS carrier is complete. In this case, the SMF network element completes a process of allocating an SM context to the GBR QoS flow needed to transfer the
[00114] [00114] It should be noted that the AMF network element can automatically allocate the EPS carrier ID to the GBR QoS flow corresponding to the PDU session modification procedure. That is, regardless of whether the GBR QoS stream needs to be transferred to the 4G network, the AMF network element allocates the EPS carrier ID to the GBR QoS stream. For example, before the SMF network element determines whether the GBR QoS stream needs to be transferred to the 4G network, the AMF network element allocated the EPS carrier ID to the GBR QoS stream and notified the SMF network element of the EPS carrier ID. If the SMF network element determines that the GBR QoS stream does not need to be transferred to the 4G network, the SMF network element deletes the EPS carrier ID, and sends notification information to the AMF network element, to instruct the AMF to release the corresponding EPS carrier ID. If the SMF network element determines that the GBR QoS stream needs to be transferred to the 4G network, the SMF network element directly reserves the EPS carrier ID, and does not need to perform step 203.
[00115] [00115] It should be noted that a process of establishing the GBR QoS flow is actually a process of initiating the PDU session modification procedure. After the SMF network element completes the process of allocating the SM context to the GBR QoS flow, the SMF network element still needs to complete the subsequent steps of the PDU session modification procedure. The subsequent steps are the same as the corresponding steps in the PDU session modification procedure in the prior art. To save space on the specification, the subsequent steps of the PDU session modification procedure are briefly described below.
[00116] [00116] In a process in which the SMF network element establishes the EPS carrier ID for the GBR QoS stream, after the AMF network element receives the N2 SM message and the N1 SM message sent by the SMF network element, the AMF network element can send an N2 PDU session request (N2 PDU Session Request) to the RAN 5G that carries the N2 SM message, the PDU session ID, and the message of SM of N1. The SM message of N1 carries a PDU Session Modification Command. After receiving the preceding information, RAN 5G can initiate specific AN signaling between the 5G network and the UE. The RAN sends some information regarding the UE of the SMF network element to the UE, to modify a RAN resource, in the UE, necessary for the PDU session. After completing the modification, the UE sends acknowledgment information to RAN 5G. For example, the UE sends a NAS message using NAS SM signaling, to respond to the PDU session modification command. The NAS message includes the PDU session ID and the N1 SM message that carries a PDU session modification command ACK.
[00117] [00117] After receiving the acknowledgment information from the UE, RAN 5G sends an N2 PDU session ACK message to the AMF, to respond to the N2 PDU request message. Then the AMF network element forwards the RAM acknowledgment message to the SMF using the Nsmf_PDUSession_UpdateSMContext service operation, to complete the PDU session modification procedure.
[00118] [00118] It should be noted that after the AMF network element receives the N2 SM message and the N1 SM message sent by the SMF network element, the AMF network element determines that the UE is in an inactive management state Connection Management Idle, CM-IDLE. In this case, the AMF initiates asynchronous type interaction, and reserves an SM request corresponding to the PDU session. Then the AMF network element initiates interaction between the AMF network element and the UE, and interaction between the AMF network element and the RAN 5G. For example, after the UE enters a connected connection management state (Connection Management Connected, CM-CONNECTED), the AMF network element brings the SM request message to the UE and the RAN 5G.
[00119] [00119] In addition, it should be noted that the SMF network element may need to update an N4 session. In this case, the SMF network element sends an N4 session change request message to the UPF network element. The message carries an N4 session ID. Usually, the SMF network element can still send some updated QoS parameters or updated deployment information such as UL update to the UPF network element using this step. If the SMF network element obtains the PCF network element's PCC rule, the SMF network element still needs to send a notification message, to notify the PCF network element if the corresponding PCC rule is executed. A specific format of the notification message is not limited in this document.
[00120] [00120] A specific implementation of the session management method in this modality of this request is described below using a specific example. With reference to FIGS. 3A and 3B, FIGS. 3A and 3B are a flow chart of an example of a session management method according to an embodiment of this request. In this specific implementation, a PDU session modification procedure is triggered by the UE, and an SMF network element determines, using a locally deployed static PCC rule, whether a GBR QoS flow corresponding to the PDU session modification procedure it is a GBR QoS stream needed to transfer the UE from a 5G network to a 4G network, and an AMF network element allocates an EPS carrier ID on the 4G network to a GBR QoS stream that needs to be transferred for the 4G network. As shown in FIGS. 3A and 3B, the method includes the following steps.
[00121] [00121] Step 301: UE sends a NAS message to an AMF network element.
[00122] [00122] In a possible implementation, the NAS message includes a PDU session ID and an N1 SM message that carries a PDU session modification request. The SM message carries service information from the UE, and the service information includes IP filtering information, media information (bandwidth, instability, a delay, and the like), and the like. Of course, the NAS message can also include other information. This is not limited in this document.
[00123] [00123] Step 302: The AMF network element triggers an Nsmf_PDUSession_UpdateSMContext service operation with an SMF network element.
[00124] [00124] In a possible implementation, the AMF network element forwards the SM message of N1 and the PDU session ID in a NAS message to the SMF network element using the Nsmf_PDUSession_UpdateSMContext service operation.
[00125] [00125] Step 303: The SMF network element initiates a PDU session modification procedure, and determines that a GBR QoS stream corresponding to the PDU session modification procedure is a GBR QoS stream necessary for transferring the UE from a 5G network to a 4G network.
[00126] [00126] In a possible implementation, once a static PCC rule is implemented locally in the SMF network element, the SMF network element generates a 5G PCC rule based on the service information in the N1 SM message. The 5G PCC rule includes a 5G QoS parameter, such as a QCI, a GBR, an MBR, an ARP, precedence, and an uplink / downlink TFT. The SMF network element verifies that the locally generated 5G QoS parameter includes GBR information used to establish a GBR QoS flow. For example, the QoS 5G parameter includes three pieces of GBR information, or it can certainly include only one piece of GBR information. This is not limited in this document. In the description below, an example in which the 5G QoS parameter includes three pieces of GBR information is used for description.
[00127] [00127] Next, the SMF network element determines, based on at least one piece of information in a DNN and operation policy information, the QoS parameter, indication information that indicates interworking between a first standard communications network and a second standard communications network, and similar, if a GBR QoS flow to be established needs to be transferred to the 4G network. Specifically, the SMF network element can determine, based on the DNN, the QoS parameter, and the indication information that indicates interworking between the first standard communications network and the second standard communications network, the GBR QoS flow that needs to be established; or can determine, based on the operator policy information, the QoS parameter, and the indication information that indicates interworking between the first standard communications network and the second standard communications network, the GBR QoS flow that needs to be established; or the SMF network element determines, based on the DNN, the operator policy information, the QoS parameter, and the indication information that indicates interworking between the first standard communications network and the second standard communications network, the flow GBo QoS that needs to be established. The SMF network element can pre-store any of the three determination modes, or it can simultaneously store the three modes. When the determination is performed, another network element can instruct the SMF network element to use one of the three modes, or the SMF network element flexibly selects a mode from among the three modes based on an actual situation. This is not limited in this document.
[00128] [00128] The SMF network element determines, based on the operator policy information, the QoS parameter, and the indication information that indicates interworking between the first standard communications network and the second standard communications network, three flows of information. GBR QoS that need to be established, and determines that a first GBR QoS stream and a second GBR QoS stream are required for transfer from the UE to the 4G network, and that the third GBR QoS stream is not required for transfer from the UE to the 4G network.
[00129] [00129] It should be noted that when a plurality of GBR QoS flows needs to be established in the PDU session modification procedure, the SMF network element needs to determine each GBR QoS flow, and a way of determining each flow GBo QoS is described in step a above. Certainly, the SMF network element can first classify the plurality of GBR QoS streams, and then select one GBR QoS stream from each class. A determination result for GBR QoS flows is a determination result for each GBR QoS flow. Therefore, a speed of determination can be accelerated, and the energy consumption of the SMF network element can be reduced.
[00130] [00130] Step 304: The SMF network element allocates a 4G QoS parameter to each GBR QoS stream that needs to be transferred to the 4G network.
[00131] [00131] When the SMF network element determines that the first GBR QoS stream and the second GBR QoS stream are required for transfer from the UE to the 4G network, and that the third GBR QoS stream is not required for transfer from the UE to the 4G network, the SMF network element separately maps corresponding 4G PCC rules to the first GBR QoS stream and the second GBR QoS stream. A PCC rule corresponding to each GBR QoS stream includes a 4G QoS parameter, and the QoS parameter
[00132] [00132] However, since the third GBR QoS stream does not need to be transferred to the 4G network, the SMF network element does not map a corresponding 4G QoS parameter to the third GBR QoS stream. That is, a QoS parameter corresponding to the third GBR QoS stream includes only one 5G QoS parameter.
[00133] [00133] Step 305: The SMF network element triggers the Nsmf_PDUSession_UpdateSMContext service operation with an AMF network element, to obtain an EPS carrier ID on the 4G network, corresponding to the GBR QoS flow that needs to be transferred to the 4G network.
[00134] [00134] After the SMF separately maps the corresponding 4G PCC rules to the first GBR QoS stream and the second GBR QoS stream, the SMF network element sends an N2 SM message and an SM message from N1 to the AMF network element using the Nsmf_PDUSession_UpdateSMContext service operation. The N2 SM message includes the PDU session ID, QoS profiles corresponding to the first GBR QoS stream and the second GBR QoS stream respectively, and an AMBR session parameter. The SM message from N1 includes a session modification command. The session modification command includes the PDU session ID, QoS rules corresponding to the first GBR QoS stream and the second GBR QoS stream respectively, and the AMBR session parameter.
[00135] [00135] The AMF network element determines that the N2 SM message includes a QoS profile corresponding to the first GBR QoS flow and a QoS profile corresponding to the second GBR QoS flow, and then the network element AMF allocates EPS carrier IDs separately on the 4G network to the first GBR QoS stream and the second GBR QoS stream. Since the N2 SM message does not include a QoS profile corresponding to the third GBR QoS stream, the AMF network element does not allocate an EPS carrier ID on the 4G network to the third GBR QoS stream. Certainly, the AMF network element can determine, using other information in the Nsmf_PDUSession_UpdateSMContext service operation, whether to allocate an EPS carrier ID on the 4G network to a GBR QoS flow. For example, the Nsmf_PDUSession_UpdateSMContext service operation can carry indication information sent by the SMF network element. The indication information is used to notify the AMF network element of a GBR QoS stream that needs to be transferred to the 4G network. Alternatively, the AMF network element can determine, based on the QoS rule in the N1 SM message, whether to allocate the EPS carrier ID on the 4G network to the GBR QoS stream. Details are not described in this document.
[00136] [00136] Step 306: The AMF network element sends a N2 PDU session request to RAN 5G.
[00137] [00137] The AMF network element sends, to RAN 5G in the N2 PDU session request, the N2 SM message, the PDU session ID, and an N1 SM message that carries the modification command of PDU session that are sent from the SMF network element.
[00138] [00138] Step 307: RAN 5G receives the PDU session request, and sends AN signaling to the UE.
[00139] [00139] The RAN 5G sends, to the UE using the signaling of AN, the SM message of N1 that carries the PDU session modification command.
[00140] [00140] Step 308: The UE receives the signaling from AN, and modifies a RAN 5G resource in a PDU session corresponding to the N1 SM message.
[00141] [00141] Step 309: The UE sends a PDU session modification command ACK to RAN 5G.
[00142] [00142] Step 310: RAN 5G receives the PDU session modification command ACK, and sends an N2 PDU session ACK to the AMF network element.
[00143] [00143] After receiving the PDU session modification command ACK sent by the UE, RAN 5G determines that the UE has completed the content corresponding to the PDU session modification command, and then generates and sends the PDU session modification ACK. N2 PDU, to respond to the N2 PDU session request sent by the AMF network element.
[00144] [00144] Step 311: The AMF network element receives the N2 PDU session ACK and forwards the RAN acknowledgment message to the SMF using the Nsmf_PDUSession_UpdateSMContext service operation, to complete the PDU session modification procedure.
[00145] [00145] Next with reference to FIGS. 4A and 4B, FIGS. 4A and 4B are a flow chart of another example of a session management method according to an embodiment of this request. In the specific implementation, a PDU session modification procedure is triggered by an AF, and the AMF network element allocates an EPS carrier ID, on a 4G network, to a GBR QoS flow that needs to be transferred to the 4G network. As shown in FIGS. 4A and 4B, the method includes the following steps.
[00146] [00146] Step 401: An AF network element initiates a PDU session modification procedure, and sends UE service information to a PCF network element.
[00147] [00147] In a possible implementation, the service information includes IP filtering information, media information (bandwidth, instability, a delay, and the like), and the like.
[00148] [00148] Step 402: The PCF network element receives the service information, and generates a PCC rule based on the service information.
[00149] [00149] After receiving the service information, the PCF network element first generates, based on the service information, a PCC 5G rule corresponding to the PDU session modification procedure. The 5G PCC rule includes a 5G QoS parameter, such as a 5QI, GBR, MBR, ARP, and uplink / downlink data packet filtering information.
[00150] [00150] If the PCF network element determines that the 5G QoS parameter includes GBR information, the PCF network element determines, based on a DNN, the 5G QoS parameter, operator policy information, and the like, whether a GBR QoS stream corresponding to GBR needs to be transferred to a 4G network. If the PCF network element determines that the GBR QoS stream needs to be transferred to the 4G network, the PCF network element allocates a corresponding 4G PCC rule to the GBR QoS stream. The 4G PCC rule includes a 4G QoS parameter, such as a QCI, a GBR, an MBR, an ARP, precedence, and an uplink / downlink TFT. Alternatively, if the PCF network element determines that the GBR QoS flow does not need to be transferred to the 4G network, the PCF network element does not allocate a corresponding 4G PCC rule to the GBR QoS flow. That is, the PCC rule generated by the PCF network element based on the service information can include the PCC 5G rule and the PCC 4G rule, or it can include only the PCC 5G rule.
[00151] [00151] Step 403: The PCF network element sends the generated PCC rule to an SMF network element.
[00152] [00152] In this modality of this request, the PCF network element can send the PCC rule separately. For example, after generating the PCC 5G rule, the PCF network element sends the PCC 5G rule directly to the SMF network element, so that the SMF network element allocates a QFI to the GBR QoS stream corresponding to the GBR, to establish the GBR QoS flow. Then after generating the 4G PCC rule corresponding to the GBR QoS flow, the PCF network element sends the 4G PCC rule to the SMF network element. The PCF network element can send the generated 5G PCC rule and the 4G PCC rule to the SMF network element together after determining that the GBR QoS stream needs to be transferred to the 4G network. This is not limited in this document.
[00153] [00153] Step 404: The SMF network element receives the PCC rule, and determines, based on the PCC rule, that the GBR QoS flow needs to be transferred to the 4G network.
[00154] [00154] After receiving the PCC rule, the SMF network element determines, based on whether the PCC rule includes the 4G PCC rule, whether the GBR QoS flow needs to be transferred to the 4G network. When it is determined that the PCC rule includes the 4G PCC rule, the SMF network element determines that the GBR QoS stream needs to be transferred to the 4G network. When it is determined that the PCC rule does not include the 4G PCC rule, the SMF network element determines that the GBR QoS stream does not need to be transferred to the 4G network.
[00155] [00155] In this modality of this request, an example in which the SMF network element determines that the QoS flow of GBR needs to be transferred to the 4G network is used for description. In this case, the SMF network element obtains the 4G QoS parameter from the GBR QoS stream using the PCC rule sent by the PCF network element.
[00156] [00156] Step 405: The SMF network element triggers a Namf_Communication_N1N2MessageTransfer service operation with the AMF network element, to obtain an EPS carrier ID corresponding to the GBR QoS flow and which is on the 4G network.
[00157] [00157] After obtaining the 4G QoS parameter from the GBR QoS flow, the SMF network element triggers the Namf_Communication_N1N2MessageTransfer service operation with the AMF network element, and sends an N2 SM message and an N1 SM message to the AMF network element. The N2 SM message includes a PDU session ID, a QoS profile corresponding to the GBR QoS flow, and an AMBR session parameter. The SM message from N1 includes a session modification command. The session modification command includes the PDU session ID, a QoS rule corresponding to the GBR QoS flow, and the AMBR session parameter.
[00158] [00158] If the AMF network element determines that the N2 SM message includes the QoS profile corresponding to the GBR QoS stream, the AMF network element allocates the EPS carrier ID, on the 4G network, to the third stream GBo QoS. Certainly, the AMF network element can determine, using other information in the Namf_Communication_N1N2MessageTransfer service operation, whether to allocate the EPS carrier ID on the 4G network to the GBR QoS flow. For example, the Namf_Communication_N1N2MessageTransfer service operation can carry indication information sent by the SMF network element. The indication information is used to notify the AMF network element of a GBR QoS stream that needs to be transferred to the 4G network. Alternatively, the AMF network element can determine, based on the QoS rule in the N1 SM message, whether to allocate the EPS carrier ID on the 4G network to the GBR QoS stream. Details are not described in this document.
[00159] [00159] Step 406: The AMF network element sends an N2 PDU session request to a 5G RAN.
[00160] [00160] Step 407: RAN 5G receives the N2 PDU session request, and sends AN signaling to the UE.
[00161] [00161] Step 408: The UE receives the signaling from AN, and modifies a resource of RAN 5G in a PDU session corresponding to the SM of N1.
[00162] [00162] Step 409: The UE sends a PDU session modification command ACK to RAN 5G.
[00163] [00163] Step 410: RAN 5G receives the PDU session modification command ACK, and sends an N2 PDU session ACK to the AMF network element.
[00164] [00164] Step 411: The AMF network element receives the
[00165] [00165] Steps 406 to 411 are the same as steps 306 to 311, and details are not described again in this document.
[00166] [00166] Step 412: The SMF network element sends indication information to the PCF network element.
[00167] [00167] In this modality of this request, the PCC rule is generated by the PCF network element. Therefore, after the execution of the PCC rule, the SMF network element can send the indication information to the PCF network element, to notify the PCF network element that the corresponding PCC rule has been executed, in order to complete the modification procedure. of PDU session.
[00168] [00168] In the preceding technical solutions, a control policy network element or a session management network element selects a GBR QoS flow in a GBR QoS flow establishment process, to ensure that a context of SM corresponding to a second communications system is allocated to only one GBR QoS stream that needs to be transferred to the second communications system, and an SM context corresponding to the second communications system is not established for a GBR QoS stream that does not need to be transferred to the second communications system. Likewise, the session management network element does not need to maintain the SM context that corresponds to the second communications system and that is from the GBR QoS flow that does not need to be transferred to the second communications system.
[00169] [00169] In a second aspect, in the state of the art, when the UE is transferred from a 5G network to a 4G network, an SMF network element selects some GBo QoS flows specific to the UE, so that the QoS flows of specific GBRs do not need to be transferred to the 4G network. In addition, transferring the UE from the 5G network to the 4G network is substantially selecting an important data radio bearer (Data Radio Bearer, DRB) from the 5G network, and transferring the selected data radio bearer to the 4G network. However, there are a plurality of types of DRBs, such as a standard carrier, a dedicated GBR carrier, and a non-GBR carrier. It can be learned that the important DRB may not be able to be selected accurately from the 5G network using a way to select only one QoS stream of GBR in the prior art. Consequently, an unnecessary packet data network (PDN) connection can be established in a state-of-the-art transfer process, wasting signaling and channel resources.
[00170] [00170] Because of this, the modalities of this request provide a method of interworking between different systems. In the method, a session management network element in a first communications system receives session context request information sent by an access management network element in the first communications system. The session context request information is used in the first communications system. The session context request information is used to obtain a session context that is from a terminal device in the first communications system and that corresponds to a second communications system. The session management network element then determines whether there is a dedicated quality of service flow in a session corresponding to the session context request, and then sends the session context to the access management network element. in which there is a dedicated service quality flow. Thus, if the dedicated quality of service flow does not exist in the session, the session management network element does not need to send the session context to the access management network element. Therefore, a PDN connection to the session context in which there is no dedicated quality of service flow does not need to be established in the second communications system, thereby reducing signaling and channel resources.
[00171] [00171] The method provided in the modalities of this application is described below with reference to the attached drawings. With reference to FIGS. 5A and 5B, FIGS. 5A and 5B are a flow chart of a method of interworking between different systems according to one embodiment of this application. The method can be applied to the interworking architecture shown in FIG. 1. A session management network element can be the SMF network element in FIG. 1, and an access management network element can be an AMF network element in FIG. 1. Of course, if the method is applied to a different interworking architecture, the session management network element and the access management network element can also be other elements. This is not limited in this document. In the following description, an example is used in which the session management network element is the SMF network element and the access management network element is the AMF network element. The method can include the following steps.
[00172] [00172] Step 501: If it is determined to transfer UE from 5G to 4G, a RAN 5G sends a transfer message requested (Handover Required) to an AMF network element.
[00173] [00173] In this embodiment of this request, the requested transfer message includes a target base station ID (Target eNB ID) and a transparent source to target container (Source to Target Transparent Container). Certainly, the requested transfer message can also include another parameter. This is not limited in this document.
[00174] [00174] Step 502: The AMF network element receives the requested transfer message, and sends a requested SM 4G context message to an SMF network element.
[00175] [00175] After receiving the requested transfer message, the AMF network element determines, based on the target eNB ID included in the requested transfer message, that the UE needs to be transferred from the 5G network to an E-UTRAN of the 4G network. The AMF network element then sends the SM 4G context request message to the SMF network element, to request an EPS carrier context, that is, an SM 4G context.
[00176] [00176] It should be noted that the UE can be served by a plurality of SMFs. In this case, the AMF network element needs to send the SM 4G context request message to all SMF network elements that serve the UE. If the UE is in a mobile state, the AMF network element requests, from the virtual session management function (V-SMF) network element, an SM 4G context corresponding to the UE.
[00177] [00177] Step 503: The SMF network element receives the SM 4G context request message, and determines whether there is a dedicated QoS flow in a session corresponding to a UE SM 4G context .
[00178] [00178] After receiving the SM 4G context request message, the SMF network element obtains all PDU sessions corresponding to the UE, and then the SMF network element determines each PDU session, to determine if there is any flow dedicated QoS flow, including a GBR QoS flow and a non-GBR QoS flow, different from a standard QoS flow in the PDU session.
[00179] [00179] It should be noted that if a plurality of SMF network elements serve the UE, each SMF network element that serves the UE needs to perform the preceding determination process on all PDU sessions corresponding to the UE.
[00180] [00180] Step 504: The SMF network element sends, to the AMF network element, an SM 4G context included in a PDU session in which there is a dedicated QoS flow.
[00181] [00181] When the SMF network element determines that there is a dedicated QoS flow in a PDU session corresponding to the UE, the SMF network element adds, to an SM context response message (SM Context Response) sent to the element AMF network settings, SM 4G contexts corresponding to the standard QoS flow and GBR QoS flow that are included in the PDU session. The context of
[00182] [00182] Alternatively, when the SMF network element determines that there is no dedicated QoS flow in a session corresponding to the UE, the SMF network element does not add, to an SM context response message (SM Context Response) sent to the AMF network element, an SM 4G context corresponding to the standard QoS flow in the PDU session. In addition, the SMF network element can also trigger a procedure to release the PDU session.
[00183] [00183] Step 505: The SMF network element receives the SM 4G context request message, and determines whether there is a service data flow (Service Data Flow, SDF) in a standard QoS flow in the session corresponding to the context EU SM 4G.
[00184] [00184] After receiving the SM 4G context request message, the SMF network element obtains all PDU sessions corresponding to the UE, and then the SMF network element determines the standard QoS flow in each PDU session, to determine whether SDF exists in the standard QoS flow in the PDU session.
[00185] [00185] It should be noted that if a plurality of SMF network elements serve the UE, each SMF network element that serves the UE needs to perform the precedent determination process on the standard QoS flows in all PDU sessions corresponding to the UE.
[00186] [00186] Step 506: The SMF network element sends to the AMF network element, an SM 4G context included in a PDU session in which the SDF exists in the standard QoS flow.
[00187] [00187] When the SMF network element determines that the SDF exists in the standard QoS flow in a session corresponding to the UE, the SMF network element adds, to the SM context response message (SM Context Response) sent to the AMF network, an SM 4G context corresponding to the PDU session. The SM 4G context includes information such as an EPS carrier ID, a QoS parameter, and an uplink / downlink TFT.
[00188] [00188] Alternatively, when the SMF network element determines that there is no SDF in the standard QoS flow in a PDU session corresponding to the UE, the SMF network element does not add, to the SM context response message sent to the AMF network, an SM 4G context corresponding to the PDU session. In addition, the SMF network element can also trigger a procedure to release the PDU session.
[00189] [00189] It should be noted that the SM 4G context that is sent from the SMF network element and that corresponds to the PDU session can be an SM 4G context selected using the session management method in the first aspect, or it can be an SM 4G context that is not selected using the session management method in the first aspect, that is, it can be all SM 4G contexts corresponding to the PDU session. This is not limited in this document.
[00190] [00190] Furthermore, it should be noted that in a process of transferring the UE from the 5G network to the 4G network, the SMF network element can perform only step 503 and step 504, and not perform step 505 and step 506, or it can perform only step 505 and step 506, and not perform step 503 and step 504. Alternatively, the SMF network element can perform not only step 503 and step 504, but also step 505 and step 506. This is not limited in this embodiment of this order.
[00191] [00191] Furthermore, it should be noted that when the SMF network element performs not only step 503 and step 504, but also step 505 and step 506, the SMF network element can perform reordering in a step order 503 to step 506. For example, the SMF network element can first perform step 503, then perform step 505, then perform step 504 and finally perform step 506; or the SMF network element can first perform step 503 and step 505, and then simultaneously perform step 504 and step 506. This is not limited in this document.
[00192] [00192] Step 507: The AMF network element receives the 4G SM context corresponding to the UE, selects an MME network element, and sends a Relocation Request message to the MME network element.
[00193] [00193] The relocation request message includes a target E-UTRAN Node ID (Target E-UTRAN Node ID), the transparent source-to-target container, an evolved package management system terminal device context session mobility and management (mapped MM and SM EPS UE Context) that carries standard and dedicated GBR carriers, SGW addresses from a control plan and a user plan, and tunnel endpoint identifiers (Tunnel Endpoint Identifier, TEID) control plan and user plan.
[00194] [00194] Step 508: The MME network element receives the relocation request message, selects a new SGW, and sends, on each UE PDN connection, a Create Session Request message to the new SGW.
[00195] [00195] In a possible implementation, the MME network element can select the new SGW based on the SGW address and the TEIDs of the control plan and the user plan in the relocation request message.
[00196] [00196] Step 509: SGW receives the create session request message, allocates a local resource to each PDN connection, and returns a create session response message (Create Session Response) to the MME network element.
[00197] [00197] The local resource can be some radio parameters that are used to ensure normal service execution between base stations, for example, it can be a service transfer threshold (Handover Threshold, RSRP), a filtering coefficient, and similar.
[00198] [00198] Step 510: After receiving the creation session response message, the MME network element sends a transfer request message to a target E-UTRAN Node.
[00199] [00199] The transfer request message is used to request that the target E-UTRAN Node allocate a carrier resource, and the message can include a list of EPS carrier IDs for which radio carrier resources need to be established in the target E-UTRAN node.
[00200] [00200] Step 511: After receiving the transfer request message, the target E-UTRAN Node allocates a corresponding resource to the UE, and returns a transfer request acknowledgment message (Handover Request Acknowledge) to the MME network element.
[00201] [00201] The transfer request acknowledgment message includes a transparent target-to-source container, an EPS Bearers setup list, and an EPS Bearers failed configuration list. to steup list).
[00202] [00202] Step 512: After receiving the transfer request acknowledgment message, the MME network element sends a Relocation Response message to the AMF network element.
[00203] [00203] The relocation response message includes a cause value (Cause), a list of radio network settings resources (List of Set Up RABs), the list of EPS bearers setup list , an MME Tunnel Endpoint Identifier for Control Plane, a radio access network cause value (RAN Cause), an MME Address for Control Plan (MME Address for Control Plane), the transparent container from target to source, and terminal identifier (s) of address (es) and tunnel for data forwarding (Address (es) and TEID (s) for Data Forwarding).
[00204] [00204] Step 513: After receiving the relocation response message, the AMF network element sends a handover command message to the source RAN 5G.
[00205] [00205] Step 514: The source RAN 5G forwards the transfer command message to the UE.
[00206] [00206] The transfer command message includes a transparent container, and the transparent container includes some radio parameters that need to be sent from the E-UTRAN Node to the source RAN 5G.
[00207] [00207] Step 515: The UE executes the transfer command.
[00208] [00208] After receiving the transfer command, the UE executes the command to associate an allocated EPS holder ID with a corresponding QoS flow, and excludes a QoS flow that is not associated with the EPS holder ID. In this case, the UE can send a complete transfer message to RAN 5G, to complete the network transfer.
[00209] [00209] Step 516: When the UE successfully accesses the target E-UTRAN Node, the target E-UTRAN Node sends a handover Notify message to the MME network element.
[00210] [00210] Step 517: For all bearers in each established session connection (PDU Connection) in the UE, the MME network element sends a modified bearer request message (Modify Bearer Request) to the SGW.
[00211] [00211] Step 518: SGW sends the modified carrier request to the SMF network element for each PDN connection.
[00212] [00212] Specifically, step 518 is mainly divided into two steps: first, SGW finds a corresponding PDN portal (PDN gateway, PGW) based on an SMF network element address from the MME network element. In this step, SGW sends allocated TEID (including a control plan TEID and a user plan TEID) to PGW, and an SMF network element control plan portal (SMF PDN gateway-Control plane, SMF + PGW -C) reserves the
[00213] [00213] Step 519: The SMF network element executes the modified carrier request and reallocates a carrier to the 4G network.
[00214] [00214] Specifically, the SMF network element control plan portal (SMF PDN gateway-Control plane, SMF + PGW-C) locally excludes a QoS flow to which an EPS carrier ID is not allocated. Since the standard QoS flow has a “everyone-compatible” filter, PGW maps an IP flow from the excluded QoS flow to the standard QoS flow.
[00215] [00215] Step 520: The SMF sends a modified bearer response message (Modify Bearer Response) to SGW.
[00216] [00216] In this way, a user plan is established which is for each of a standard carrier and a dedicated GBR carrier and that is between the UE, the target E-UTRAN Node, the SGW, and the element of SMF network.
[00217] [00217] Step 521: SGW sends the modified carrier reply message to the MME network element.
[00218] [00218] Step 522: The SMF network element initiates a dedicated carrier activation procedure for a non-GBR QoS flow, to re-establish a dedicated non-GBR carrier corresponding to the non-GBR QoS flow.
[00219] [00219] It should be noted that if dynamic PCC is deployed in a PCF, this step can be initiated by the PCF network element.
[00220] [00220] In the preceding transfer process, when an access management network element requests, from a session management network element, an SM context corresponding to a second communications system, for a PDU session in which no there is a dedicated QoS flow, the session management network element does not send to the access management network element an SM context corresponding to a standard QoS flow in the PDU session, in order to avoid establishing a corresponding connection of PDN on the side of the second communications system, thereby reducing signaling and channel resources.
[00221] [00221] Based on the previous modalities, one modality of this application also provides a network device. The network apparatus can implement corresponding steps performed by a session management network element in the mode shown in FIG. 2 to FIGS. 4A and 4B. With reference to FIG. 6, a network device 600 includes a processor 601.
[00222] [00222] The 601 processor can be a central processing unit (CPU) or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), it can be one or more integrated circuits configured to control program execution, or it can be a baseband chip, or similar.
[00223] [00223] The network device can also include a memory, and the memory can be connected to the 601 processor using a bus structure, a star structure, or another structure. There may be one or more memories. Memory can be read-only memory
[00224] [00224] Processor 601 is configured for: when a guaranteed GBR bit rate flow from a terminal device in a first communications system is established, determine, by the network device in the first communications system, that the GBR flow is a GBR stream needed to transfer the terminal device from the first communications system to a second communications system; and to establish, for the GBR flow, a session context corresponding to the second communications system.
[00225] [00225] In a possible implementation, the 601 processor is specifically configured to: determine, based on at least one of a PCC load and policy control rule, an operator policy, and a DNN data network name, which the GBR stream is the GBR stream needed to transfer the terminal device from the first communications system to the second communications system.
[00226] [00226] In a possible implementation, the network device also includes a receiver 602. The receiver 602 can be connected to the processor 601 using a bus structure, a star structure, or another structure, or it can be connected to the processor 601 using a dedicated connection cable.
[00227] [00227] Receiver 602 is specifically configured to: receive PCC rule information sent by the policy control network element, where the PCC rule information includes a PCC rule that is from the GBR stream and that corresponds to the second communications system.
[00228] [00228] Processor 601 is specifically configured to: determine, based on PCC rule information, that the GBR stream is the GBR stream necessary for transferring the terminal device from the first communications system to the second communications system.
[00229] [00229] In a possible implementation, receiver 602 is further configured to receive service information sent by the terminal device.
[00230] [00230] Processor 601 is specifically configured to: determine, based on service information, operator policy, and DNN data network name, that the GBR stream is the GBR stream required to transfer the terminal device from the first communications system to the second communications system.
[00231] [00231] In a possible implementation, the PCC rule includes a GBR parameter, an MBR multiband band indicator and an IP filter.
[00232] [00232] Code corresponding to the previous session management method is built into a chip by the design and programming of processor 601 and receiver 602, so that the chip can execute the previous session management method when it is executed. How to design and program the 601 processor and the 602 receiver is a technology well known to a person skilled in the art, and details are not described again in this document.
[00233] [00233] Based on the previous modalities, one modality of this application also provides a network device. The network apparatus can implement corresponding steps performed by a policy control network element in the mode shown in FIG. 2 to FIGS. 4A and 4B. With reference to FIG. 7, the network apparatus 700 includes a receiver 701, a processor 702 and a transmitter 703.
[00234] [00234] Processor 702 can be a central processing unit (CPU) or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), it can be one or more integrated circuits configured to control program execution, or it can be a baseband chip, or similar.
[00235] [00235] Receiver 701 and transmitter 703 can be connected to processor 702 using a bus frame, star structure, or other structure, or they can be connected separately to processor 702 using a dedicated connection cable.
[00236] [00236] The network device can also include a memory, and the memory can be connected to processor 702 using a bus structure, a star structure, or another structure. There may be one or more memories. The memory can be a read-only memory (Read Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk memory, or the like. The memory can be configured to store program code required by the 702 processor to perform a task, and the memory can be further configured to store data.
[00237] [00237] Receiver 701 is configured to receive service information from a terminal device or an application network element.
[00238] [00238] Processor 702 is configured to generate PCC policy and load control rule information based on at least one of an operator policy and a DNN data network name, service information, and an interworking capability from the terminal device of a first standard communications network to a second standard communications network. The PCC rule information includes at least one PCC rule that is from the GBR stream and that corresponds to a first communications system. The first communications system uses the first standard communications network, and the second communications system uses the second standard communications network.
[00239] [00239] Transmitter 703 is configured to send the PCC rule to a session management network element.
[00240] [00240] In a possible implementation, the PCC rule includes a GBR parameter, an MBR multi-band indicator and an IP filter.
[00241] [00241] Code corresponding to the previous session management method is built into a chip by the design and programming of receiver 701, processor 702 and transmitter 703, so that the chip can execute the previous session management method when it is executed . How to design and program the 701 receiver, the 702 processor and the 703 transmitter is a technology well known to a person skilled in the art, and details are not described again in this document.
[00242] [00242] Based on the previous modalities, one modality of this application also provides a network device. The network apparatus can implement corresponding steps performed by a session management network element in the mode shown in FIG. 2 to FIGS. 4A and 4B. With reference to FIG. 8, the network apparatus 800 includes a determination unit 801 and an establishment unit
[00243] [00243] In real application, network element devices corresponding to the determination unit 801 and the establishment unit 802 may be processor 601 in FIG. 6.
[00244] [00244] The determination unit 801 is configured for: when a GBR guaranteed bit rate flow from a terminal device in a first communications system is established, determine, by the network device in the first communications system, that the flow of GBR is a GBR stream needed to transfer the terminal device from the first communications system to a second communications system.
[00245] [00245] The establishment unit 802 is configured to establish, for the GBR flow, a session context corresponding to the second communications system.
[00246] [00246] In a possible implementation, the determination unit 801 is specifically configured to: determine, based on at least one of a PCC policy and loading control rule, an operator policy and a DNN data network name, that the GBR stream is the GBR stream needed to transfer the terminal device from the first communications system to the second communications system.
[00247] [00247] In a possible implementation, the network device also includes: a first receiving unit 803, configured to receive PCC rule information sent by the policy control network element, where the PCC rule information includes a rule that is from the GBR stream and that corresponds to the second communications system.
[00248] [00248] The determination unit 801 is specifically configured to: determine, based on the PCC rule information, that the GBR flow is the GBR flow necessary to transfer the terminal device from the first communications system to the second communication system communications.
[00249] [00249] In a possible implementation, the network device also includes: a second receiving unit 804, configured to receive service information sent by the terminal device.
[00250] [00250] The determination unit 801 is specifically configured to: determine, based on the service information, the operation policy and the DNN data network name, that the GBR stream is the GBR stream needed to transfer the device terminal of the first communications system to the second communications system.
[00251] [00251] In a possible implementation, the PCC rule includes a GBR parameter, an MBR multi-band indicator parameter and an IP filter.
[00252] [00252] Based on the previous modalities, one modality of this application also provides a network device. The network apparatus can implement corresponding steps performed by a policy control network element in the mode shown in FIG. 2 to FIGS. 4A and 4B. With reference to FIG. 9, the network apparatus 900 includes a receiving unit 901, a processing unit 902 and a sending unit 903.
[00253] [00253] In real application, a network element device corresponding to the receiving unit 901 can be the receiver 701 in FIG. 7, a network element device corresponding to processing unit 902 can be processor 702 in FIG. 7, and a network element device corresponding to sending unit 903 can be transmitter 703 in FIG. 7.
[00254] [00254] Receiving unit 901 is configured to receive service information from a terminal device or an application network element.
[00255] [00255] Processing unit 902 is configured to generate PCC policy and load control rule information based on at least one of an operator policy and a DNN data network name, service information, and a interworking capability of the terminal device from a first standard communications network to a second standard communications network. The PCC rule information includes at least one PCC rule that is from the GBR stream and that corresponds to a first communications system. The first communications system uses the first standard communications network, and a second communications system uses the second standard communications network.
[00256] [00256] The sending unit 903 is configured to send the PCC rule to a session management network element.
[00257] [00257] In a possible implementation, the PCC rule includes a GBR parameter, an MBR multi-band indicator parameter and an IP filter.
[00258] [00258] In the previous technical solution, the network device selects a GBR QoS flow in a GBR QoS flow establishment process, to ensure that an SM context corresponding to the second communications system is allocated to only one flow of GBR QoS that needs to be transferred to the second communications system, and an SM context corresponding to the second communications system is not established for a GBR QoS stream that does not need to be transferred to the second communications system. Likewise, the network device does not need to maintain the SM context that corresponds to the second communications system and that is from the GBR QoS flow that does not need to be transferred to the second communications system.
[00259] [00259] Based on the previous modalities, one modality of this application also provides a network device. The network apparatus can implement corresponding steps performed by a session management network element in the manner shown in FIGS. 5A and 5B. With reference to FIG. 10, the network apparatus 1000 includes a receiver 1001, a processor 1002 and a transmitter 1003.
[00260] [00260] Processor 1002 can be a central processing unit (CPU) or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), it can be one or more integrated circuits configured to control program execution, or it can be a baseband chip, or similar.
[00261] [00261] Receiver 1001 and transmitter 1003 can be connected to processor 1002 using a bus frame, star structure, or other structure, or they can be connected separately to processor 1002 using a dedicated connection cable.
[00262] [00262] The network device can also include a memory, and the memory can be connected to processor 1002 using a bus structure, a star structure, or another structure. There may be one or more memories. The memory can be a read-only memory (Read Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk memory, or the like. The memory can be configured to store program code required by processor 1002 to perform a task, and the memory can be further configured to store data.
[00263] [00263] Receiver 1001 is configured to receive session context request information sent by an access management network element in a first communications system, where session context request information is used to obtain a session context. session that is from a terminal device in the first communications system and that corresponds to a second communications system, and the network device is in the first communications system.
[00264] [00264] Processor 1002 is configured to determine that there is a dedicated quality of service flow in a session corresponding to the session context request.
[00265] [00265] Transmitter 1003 is configured to send, to the access management network element in the first communications system, the session context corresponding to the session in which the dedicated quality of service flow exists.
[00266] [00266] In a possible implementation, processor 1002 is further configured to: determine that there is no dedicated quality of service flow in the session corresponding to the session context request; and release the session in which there is no dedicated quality of service flow.
[00267] [00267] In a possible implementation, processor 1002 is further configured to: determine that there is no SDF service data flow in a standard quality of service flow in the session corresponding to the session context request; and release the session in which there is no SDF in the standard quality of service flow.
[00268] [00268] In a possible implementation, processor 1002 is further configured to: determine that there is an SDF service data flow in the standard quality of service flow in the session corresponding to the session context request.
[00269] [00269] Transmitter 1003 is further configured to:
[00270] [00270] Code corresponding to the previous session management method is built into a chip by the design and programming of receiver 1001, processor 1002 and transmitter 1003, so that the chip can execute the previous session management method when it is executed . How to design and program the receiver 1001, processor 1002 and transmitter 1003 is a technology well known to a person skilled in the art, and details are not described again in this document.
[00271] [00271] Based on the foregoing modalities, one modality of this application also provides a network device. The network apparatus can implement corresponding steps performed by an access management network element in the mode shown in FIGS. 5A and 5B. With reference to FIG. 11, the network apparatus 1100 includes a transmitter 1101 and a receiver 1102.
[00272] [00272] Transmitter 1101 and receiver 1102 can be independent of each other, or can be integrated together. If the network device is connected to another device in a wireless mode, transmitter 1101 and receiver 1102 can be radio frequency circuits. If the network device is connected to another device in a wired mode, transmitter 1101 can be a transmit port, and receiver 1102 can be a receive port.
[00273] [00273] Transmitter 1101 is configured to: send session context request information to a session management network element in a first communications system, where session context request information is used to obtain a session context. session that is from a terminal device in the first communications system and that corresponds to a second communications system.
[00274] [00274] Receiver 1102 is configured to: receive the session context sent by the session management network element, where there is a dedicated quality of service flow in a session corresponding to the session context.
[00275] [00275] Code corresponding to the preceding interworking method is built into a chip by the design and programming of transmitter 1101 and receiver 1102, so that the chip can execute the preceding interworking method when it is executed. How to design and program the 1101 transmitter and 1102 receiver is a technology well known to a person skilled in the art, and details are not described again in this document.
[00276] [00276] Based on the previous modalities, one modality of this application also provides a network device. The network apparatus can implement corresponding steps performed by a session management network element in the manner shown in FIGS. 5A and 5B. With reference to FIG. 12, the network apparatus 1200 includes a receiving unit 1201, a first determining unit 1202 and a first sending unit.
[00277] [00277] In real application, a network element device corresponding to the receiving unit 1201 can be the receiver 1001 in FIG. 10, a network element device corresponding to the first determination unit 1202 can be processor 1002 in FIG. 10, and a network element device corresponding to the first sending unit 1203 can be transmitter 1003 in FIG. 10.
[00278] [00278] Receiving unit 1201 is configured to receive session context request information sent by the access management network element in a first communications system, where session context request information is used to obtain a context session that is from a terminal device in the first communications system and that corresponds to a second communications system, and the network device is in the first communications system.
[00279] [00279] The first determination unit 1202 is configured to determine that there is a dedicated quality of service flow in a session corresponding to the session context request.
[00280] [00280] The first sending unit 1203 is configured to send, to the access management network element in the first communications system, the session context corresponding to the session in which there is a dedicated quality of service flow.
[00281] [00281] In a possible implementation, the network device also includes: a second determination unit 1204, configured to determine that there is no dedicated quality of service flow in the session corresponding to the session context request; and a first release unit 1205, configured to release the session in which there is no dedicated quality of service flow.
[00282] [00282] In a possible implementation, the network device also includes: a third unit of determination 1206, configured to determine that there is no flow of SDF service data in a standard flow of quality of service in the session corresponding to the context request of session; and a second release unit 1207, configured to release the session in which there is no SDF in the standard quality of service stream.
[00283] [00283] In a possible implementation, the network device also includes: a fourth unit of determination 1208, configured to determine that there is an SDF service data flow in the standard quality of service flow in the session corresponding to the session context request ; and a second sending unit 1209, configured to send, to the access management network element in the first communications system, the session context corresponding to the session in which the SDF exists.
[00284] [00284] Based on the previous modalities, one modality of this application also provides a network device. The network apparatus can implement corresponding steps performed by an access management network element in the mode shown in FIGS. 5A and 5B. With reference to FIG. 13, the network apparatus 1300 includes a sending unit 1301 and a receiving unit 1302.
[00285] [00285] In real application, a network element device corresponding to sending unit 1301 can be transmitter 1101 in FIG. 11, and a network element device corresponding to the receiving unit 1302 can be the receiver 1102 in FIG. 11.
[00286] [00286] Sending unit 1301 is configured to send session context request information to a session management network element in a first communications system, where session context request information is used to obtain context session that is from a terminal device in the first communications system and that corresponds to a second communications system.
[00287] [00287] Receiving unit 1302 is configured to receive the session context sent by the session management network element, where there is a dedicated quality of service flow in a session corresponding to the session context.
[00288] [00288] The network device provided in this application may be a chip system, and the chip system may include at least one chip, and may also include another discrete component. The chip system can be positioned on the network device, and support the network device at the end of the session management method or the interworking method provided in the modalities of this order.
[00289] [00289] One embodiment of this application provides a computer storage medium, and the computer storage medium stores an instruction. When the instruction is executed on a computer, the computer executes the session management method or the interworking method.
[00290] [00290] One embodiment of this application provides a computer program product, and the computer program product stores an instruction. When the instruction is executed on a computer, the computer executes the session management method or the interworking method.
[00291] [00291] In the previous technical solutions, after the network device in the first communications system receives the session context request information used to obtain the session context that is from the terminal device in the first communications system and that corresponds to the second communications system, the network device determines whether there is a dedicated quality of service flow in the session corresponding to the session context request, and then establishes a PDN connection on the second communications system to the terminal device based on the fact that session context in which there is a dedicated service quality flow. Thus, if there is no dedicated quality of service flow in the session context, a PDN connection to the session context in which there is no dedicated quality of service flow does not need to be established in the second communications system.
[00292] [00292] All or some of the modalities mentioned above can be implemented by software, hardware, firmware, or any combination of these. When software is used, to implement the modalities, the modalities can be implemented completely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the procedure or functions according to the modalities of this order are all or partially generated. The computer can be a general purpose computer, a dedicated computer, a computer network, or other programmable devices. Computer instructions can be stored on a computer-readable storage medium or they can be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired mode (for example, a coaxial cable , an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio and microwave). The computer-readable storage medium can be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, which integrates one or more usable media. The usable medium can be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a Solid State Disk ( SSD)), or similar.
[00293] [00293] The preceding descriptions are merely specific implementations of this application, but are not intended to limit the scope of protection of this application. Any variation or replacement easily identified by a person skilled in the art within the technical scope disclosed in this application must fall within the scope of protection of this application. Therefore, the scope of protection of this claim should be subject to the scope of protection of the claims.

权利要求:
Claims (16)
[1]
1. Session management method, characterized by the fact that it comprises: when establishing a guaranteed GBR bit rate flow from a terminal device in a first communications system, determine (202), by a network management element session on the first communications system based on at least one of a PCC loading and policy control rule and an operator policy, that the GBR stream is the GBR stream needed to transfer the terminal device from the first communications system to the second communications system; and establishing, through the session management network element for the GBR flow, a session context corresponding to the second communications system.
[2]
2. Method, according to claim 1, characterized by the fact that the establishment, by the session management network element for the GBR flow, of the session context corresponding to the second communications system, comprises: establishing (203) , by the session management network element, bearer ID in the second communications system for the GBR stream.
[3]
3. Method, according to claim 2, characterized by the fact that the establishment, by the session management network element, of the bearer ID in the second communications system for the GBR flow, comprises: send, by the session management network to an AMF mobility and access management function network element, information for establishing the bearer ID in the second communications system for the GBR stream; obtain, by the session management network element from the AMF network element, the bearer ID allocated by the AMF network element.
[4]
4. Method, according to claim 2 or 3, characterized by the fact that the establishment, by the session management network element for the GBR flow, of the session context corresponding to the second communications system, further comprises: allocate (304), by the session management network element, a QoS quality of service parameter in the second communications system for the GBR flow.
[5]
5. Method according to any one of claims 1 to 4, characterized by the fact that it further comprises: determining (201), by the session management network element, that the GBR flow needs to be established.
[6]
6. Method, according to claim 1, characterized by the fact that the method further comprises: receiving, by the session management network element, the CCP rule of a policy control network element.
[7]
7. Method according to any one of claims 1 to 6, characterized in that the determination, by the session management network element based on the PCC rule, that the GBR flow is a GBR flow necessary for transferring the terminal device from the first communications system to the second communications system, comprising: determining, by the session management network element, that the GBR stream is the GBR stream necessary for transferring the terminal device from the first communications system for the second communications system in the event that the PCC rule corresponding to the GBR stream includes a PCC rule from the first communications system and a PCC rule from the second communications system.
[8]
8. Method according to any one of claims 1 to 7, characterized in that the first communications system is a fifth generation 5G communications system, and the second communications system is a fourth generation 4G communications system .
[9]
9. Device, characterized by the fact that it comprises: at least one processor coupled to a memory, in which at least one processor is configured to execute instructions stored in memory, to enable the device to execute the method as defined in any of the claims 1 to 8.
[10]
10. Computer-readable storage medium, characterized by the fact that the medium stores an instruction, and when the instruction is executed on a computer, the computer implements the method as defined in any one of claims 1 to 8.
[11]
11. Method, characterized by the fact that it comprises: when a guaranteed bit rate (GBR) flow from a terminal device is established in a first communications system, determine (202), by a session management network element in the first communications system based on a quality of service (QoS) parameter and an operator policy, that the GBR stream is the GBR stream necessary for transferring the terminal device from the first communications system to the second communications system; sending, through the session management network element to an access and mobility management function (AMF) network element, information to allocate a bearer ID in the second communications system to the GBR stream; allocate, by the AMF network element, the carrier ID for the GBR stream; obtain, by the session management network element from the AMF network element, the bearer ID allocated by the AMF network element.
[12]
12. Method, according to claim 11, characterized by the fact that it further comprises: establishing, by the session management network element for the GBR flow, a session context corresponding to the second communications system, in which the context session comprises the carrier ID.
[13]
13. Method, according to claim 12, characterized by the fact that it further comprises: allocating (304), by the session management network element, a QoS parameter in the second communications system for the GBR flow; where the session context also comprises the QoS parameter in the second communications system.
[14]
14. Method, according to claim 11, characterized by the fact that it further comprises: determining (201), by the session management network element, that the GBR flow needs to be established.
[15]
15. Method, according to claim 11, characterized by the fact that the first communications system is a fifth generation (5G) communications system, and the second communications system is a fourth generation (4G) communications system .
[16]
16. First communications system, characterized by the fact that it comprises: a session management network element, configured to execute the method as defined in any one of claims 1, and 4 to 8, wherein the management network element session is further configured to send, to an access and mobility management function, AMF, network element, information to establish a carrier ID in the second communications system for the GBR stream; and the AMF network element, configured to allocate the carrier ID to the GBR stream, and to send the carrier ID to the session management network element, where the session context established by the management network element session comprises the bearer ID.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112020003199A2|2020-10-06|session management method, interworking method, and network device

---

JP2020529168A5|2020-11-12|

---

RU2764259C1|2022-01-14|Method for activating or deactivating user plane connection in each session

---

EP3231248B1|2020-12-23|Wifi boost with lte ip anchor

---

US9794969B2|2017-10-17|Bearer allocation method, user equipment, base station, and serving gateway

---

US20200260336A1|2020-08-13|Communication method, network element, terminal apparatus, and system

---

US11109263B2|2021-08-31|Data transmission method and data transmission apparatus

---

US11178538B2|2021-11-16|Transmission method and network device

---

US20180352594A1|2018-12-06|Radio base station, edge server, and methods therein

---

KR102267267B1|2021-06-21|Session context conversion

---

EP3614740A1|2020-02-26|User equipment, wireless communication system, and wireless communication method

---

US20220046755A1|2022-02-10|Data Forwarding Method, Apparatus, and System

---

US11259220B2|2022-02-22|Handover method and apparatus

---

BR112019020398A2|2020-04-22|relay communication method and apparatus and relay communication system

---

US10728794B2|2020-07-28|Network terminal device communication method and apparatus

---

US20210185585A1|2021-06-17|User plane setup during 5g system to evolved packet system handover

---

EP3790314A1|2021-03-10|Communication method and device

---

US20210266797A1|2021-08-26|Method and apparatus for controlling disorder of downlink data

---

TW201924466A|2019-06-16|Method and apparatus for establishing bearers in a wireless communication system

---

US20190082482A1|2019-03-14|Resource access method, apparatus, and system

---

US20210120610A1|2021-04-22|Rate Adjustment Method, Apparatus, and System

---

WO2018103009A1|2018-06-14|Method for deleting data radio bearer, user equipment and access network function entity

---

WO2017166291A1|2017-10-05|Communication method, terminal, base station, and mobility management equipment

同族专利:

---

公开号 | 公开日

---

KR20200017523A|2020-02-18|

---

KR102275935B1|2021-07-12|

---

WO2019033901A1|2019-02-21|

---

EP3641396B1|2021-10-27|

---

CN109392042B|2021-10-26|

---

JP2020529168A|2020-10-01|

---

EP3641396A1|2020-04-22|

---

EP3641396A4|2020-06-10|

---

US20200187043A1|2020-06-11|

---

CN109392042A|2019-02-26|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

CN101272600B|2007-03-23|2012-12-12|华为技术有限公司|Method for implementing bearing re-establishing, and related device|

---

CN101478743B|2008-01-03|2010-08-25|大唐移动通信设备有限公司|Method and apparatus for EPS bearing management|

---

WO2012050841A1|2010-09-28|2012-04-19|Research In Motion Corporation|Method and apparatus for releasing connection with local gw when ue moves out of the residential/enterprise network coverage|

---

US9554389B2|2012-08-31|2017-01-24|Qualcomm Incorporated|Selectively allocating quality of service to support multiple concurrent sessions for a client device|

---

US9191805B2|2012-09-24|2015-11-17|Verizon Patent And Licensing Inc.|Connecting devices to a policy charging rules function device|

---

WO2014158206A1|2013-03-29|2014-10-02|Intel Corp|Hybrid beamforming for data transmission|

---

CN107018542A|2017-03-27|2017-08-04|中兴通讯股份有限公司|The processing method of status information, device and storage medium in network system|CN110035401B|2018-01-12|2020-06-23|电信科学技术研究院有限公司|Method and equipment for controlling QoSof default service|

---

US20190313310A1|2018-04-09|2019-10-10|Nokia Technologies Oy|Session context conversion|

---

US20190313311A1|2018-04-09|2019-10-10|Mediatek Inc.|Apparatuses, service networks, and methods for handling plmn-specific parameters for an inter-plmn handover|

---

US11026124B2|2018-07-02|2021-06-01|Mediatek Inc.|Enhanced handling on 5G QoS operations|

---

KR102201023B1|2018-08-10|2021-01-11|텔레호낙티에볼라게트 엘엠 에릭슨|Methods and nodes for facilitating PDU session procedure in interworking networks|

---

US11039369B2|2018-08-10|2021-06-15|Mediatek Inc.|Handling 5G QoS rules on QoS operation errors|

---

WO2020199397A1|2019-03-29|2020-10-08|Telefonaktiebolaget Lm Ericsson |Method, apparatus for synchronization of status of qos flow in communication system|

---

CN111901446A|2019-05-05|2020-11-06|华为技术有限公司|Method and equipment for allocating and acquiring IP address|

---

US11246064B2|2019-05-06|2022-02-08|Mediatek Inc.|PDN connection supports interworking to 5GS|

---

CN111918237A|2019-05-07|2020-11-10|华为技术有限公司|Communication method and device|

---

CN112469024A|2019-09-09|2021-03-09|华为技术有限公司|Session management method and device|

---

CN112788584A|2019-11-08|2021-05-11|华为技术有限公司|Communication method and device|

---

US11212859B2|2019-11-26|2021-12-28|T-Mobile Usa, Inc.|5G avoidance during LTE-based real-time communications|

---

WO2021109095A1|2019-12-05|2021-06-10|华为技术有限公司|Inter-network interoperation method, apparatus, and system|

---

US11212699B1|2020-06-24|2021-12-28|Sprint Communications Company L.P.|Wireless guaranteed bit ratedata service|

法律状态:
2021-11-23| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

CN201710693980.1|2017-08-14|

---

CN201710693980.1A|CN109392042B|2017-08-14|2017-08-14|Session management method, inter-system interoperation method and network device|

---

PCT/CN2018/096685|WO2019033901A1|2017-08-14|2018-07-23|Session management method, method for interworking between heterogeneous systems, and network device|

---